X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C78E9D.A5FE1107@onstor-exch02.onstor.net>; Fri, 4 May 2007 15:43:34 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C78E9D.A5FE1107"
Content-class: urn:content-classes:message
Subject: RE: [Zonda] Network initial config via WebUI -- system component
Date: Fri, 4 May 2007 15:43:34 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E014B98DB@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Zonda] Network initial config via WebUI -- system component
Thread-Index: AceGwqPihkan8Qg2S4eY9s/EcZsaJAFbUWAQAJrNEuAAAHMI6g==
References: <20070424154813.653bd7a6@ripper.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E03797464@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0399431F@onstor-exch02.onstor.net>
From: "Eric Crutchlow" <eric.crutchlow@onstor.com>
To: "Charissa Willard" <charissa.willard@onstor.com>,
	"dl-Design Review" <dl-designreview@onstor.com>
Cc: "Bill Duffy" <bill.duffy@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C78E9D.A5FE1107
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

If we assume the installation is a HA (2 or more nodes), then a static =
address would be an issue since it would be duplicate.=20
=20
If we use a hard address, we could always use one of the 172.16.x.x on =
the SC2 port since SC2 is generally used via a xover cable. Just have to =
be able to reconfigure the SC2 port ip as part of the initial config.
=20
Regards,
=20
Eric

________________________________

From: Charissa Willard
Sent: Fri 5/4/2007 3:37 PM
To: dl-Design Review
Cc: Eric Crutchlow; Bill Duffy
Subject: RE: [Zonda] Network initial config via WebUI -- system =
component



1.) I discussed the initial configuration wizard with the SEs a few =
months ago. Both Eric Crutchlow and Bill Duffy thought that using a =
static IP address would be okay for now. However, the issue still =
remains as to selecting an IP address that has a high probability of =
being unique. Also, is there an issue with just going with a class C =
private address? These are the available private IP addresses for each =
class:

=20

     Class A: 10.0.0.0    - 10.255.255.255  (10/8 prefix)=20

     Class B: 172.16.0.0  - 172.31.255.255  (172.16/12 prefix)

     Class C: 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

=20

=20

2.) We could also configure a static DHCP IP address like NetApp does. =
Below are the instructions NetApp uses to set up a static DHCP IP =
address.

=20

   The NetApp QuickSetup wizard, version 1.01, has the following system =
requirements:

=20

* A NetApp filer with Data ONTAP 6.1 software or later attached to a =
network with a DHCP server=20

* The CIFS license installed on the filer=20

* A Windows NT 4.0 or Windows 2000 workstation within the same domain or =
workgroup as the new filer that has access to any remote subnet that =
contains the filer=20

=20

    Configure the following information into your DHCP server:

=20

* Filer MAC address=20

* Filer IP address with an infinite lease=20

* Any of the following optional information:=20

O Routers=20

O Default route=20

O DNS domain name=20

O DNS servers=20

O NIS domain name=20

O NIS servers=20

O WINS servers=20

O SMTP server=20

=20

3.) Lastly, there is still the possibility of using one of Zero =
Configuration (ZeroConf) technologies. There is no need to configure =
anything for this, hence the name - Zero Configuration). A browser =
plug-in is required though. Note that ZeroConf is Apple's version of =
Microsoft's UPnP. The link-local (LL) addressing feature uses addresses =
in the 169.254.0.0/16 range. Microsoft refers to this as "Automatic =
Private IP Addressing". This technology is defined in RFC 3927 (for =
IPv4).

=20

Bonjour is Apple's implementation of ZeroConf. Avahi is the ZeroConf =
implementation for Linux and BSD. Avahi contains an implementation of =
IPv4LL in the avahi-autoipd tool =
(http://avahi.org/download/avahi-autoipd.8.xml). This tool can be used =
stand-alone or as a plug-in for a DHCP client.

=20

-Charissa

=20

=20

=20

-----Original Message-----
From: Jonathan Goldick=20
Sent: Tuesday, May 01, 2007 1:37 PM
To: Andy Sharp; dl-designreview
Subject: RE: [Zonda] Network initial config via WebUI -- system =
component

=20

In your backup method with a static IP, what number do we choose?  We =
discussed this years back and could never come up with one that was =
known to be safe.  We even went as far as talking about having a small =
input device to key in the static IP address (not a popular idea). =20

=20

In general I like the new idea, we should vet some of the assumptions =
with customers, like our newly formed customer advisory board, to see if =
this is what they want.  Just thinking of possible issues relating to =
plugging a laptop directly into the 10x100 BaseT.  Do we supply the =
cables?  Must they have one of their own?

=20

=20

=20

=20

-----Original Message-----

From: Andy Sharp=20

Sent: Tuesday, April 24, 2007 3:48 PM

To: dl-designreview

Subject: [Zonda] Network initial config via WebUI -- system component

=20

I've heard that we are going to try and have a WebUI initial (install)

config thing for Zonda release, so I thought I would write up how I

think we should make the system level network part of that equation

happen.  This what I planned to do for Linux regardless of how the

config was done, rather than use a serial port.

=20

I'm asking for RFC at this time.  If there are no objections or

questions, I'll schedule a meeting if people think it's necessary.

=20

Cheers,

=20

a


------_=_NextPart_001_01C78E9D.A5FE1107
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2800.1589" name=3DGENERATOR>=0A=
<STYLE>=0A=
<!--=0A=
                        =0A=
 p.MsoNormal, li.MsoNormal, div.MsoNormal=0A=
	{margin:0in;=0A=
	margin-bottom:.0001pt;=0A=
	font-size:10.0pt;=0A=
	font-family:"Courier New";}=0A=
a:link, span.MsoHyperlink=0A=
	{color:blue;=0A=
	text-decoration:underline;}=0A=
a:visited, span.MsoHyperlinkFollowed=0A=
	{color:purple;=0A=
	text-decoration:underline;}=0A=
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText=0A=
	{margin:0in;=0A=
	margin-bottom:.0001pt;=0A=
	font-size:9.0pt;=0A=
	font-family:"Courier New";}=0A=
=0A=
div.Section1=0A=
	{page:Section1;}=0A=
-->=0A=
</STYLE>=0A=
</HEAD>=0A=
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>=0A=
<DIV dir=3Dltr>If we assume the installation is a HA (2 or more nodes), =
then a static address would be an issue since it would be duplicate. =
</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>If we use a hard address, we could always use one of the =
172.16.x.x on the SC2 port since SC2 is generally used via a xover =
cable. Just have to be able to reconfigure the SC2 port ip as part of =
the initial config.</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Regards,</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>Eric<BR></DIV>=0A=
<DIV dir=3Dltr>=0A=
<HR tabIndex=3D-1>=0A=
</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2><B>From:</B> Charissa =
Willard<BR><B>Sent:</B> Fri 5/4/2007 3:37 PM<BR><B>To:</B> dl-Design =
Review<BR><B>Cc:</B> Eric Crutchlow; Bill Duffy<BR><B>Subject:</B> RE: =
[Zonda] Network initial config via WebUI -- system =
component<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<DIV class=3DSection1>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">1.) I discussed the initial configuration =
wizard with the SEs a few months ago. Both Eric Crutchlow and Bill Duffy =
thought that using a static IP address would be okay for now. However, =
the issue still remains as to selecting an IP address that has a high =
probability of being unique. Also, is there an issue with just going =
with a class C private address? These are the available private IP =
addresses for each class:</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">&nbsp;&nbsp;&nbsp;&nbsp; Class A: =
10.0.0.0&nbsp;&nbsp;&nbsp; - 10.255.255.255&nbsp; (10/8 prefix) =
</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">&nbsp;&nbsp;&nbsp;&nbsp; Class B: =
172.16.0.0&nbsp; - 172.31.255.255&nbsp; (172.16/12 =
prefix)</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">&nbsp;&nbsp;&nbsp;&nbsp; Class C: 192.168.0.0 - =
192.168.255.255 (192.168/16 prefix)</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">2.) We could also configure a static DHCP IP =
address like NetApp does. Below are the instructions NetApp uses to set =
up a static DHCP IP address.</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">&nbsp;&nbsp; The NetApp QuickSetup wizard, =
version 1.01, has the following system requirements:</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3D"Courier New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">&#8226; A =
NetApp filer with Data ONTAP 6.1 software or later attached to a network =
with a DHCP server </SPAN></FONT></P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3D"Courier New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">&#8226; The =
CIFS license installed on the filer </SPAN></FONT></P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3D"Courier New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">&#8226; A =
Windows NT 4.0 or Windows 2000 workstation within the same domain or =
workgroup as the new filer that has access to any remote subnet that =
contains the filer </SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">&nbsp;&nbsp;&nbsp; Configure the following =
information into your DHCP server:</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3D"Courier New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">&#8226; =
Filer MAC address </SPAN></FONT></P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3D"Courier New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">&#8226; =
Filer IP address with an infinite lease </SPAN></FONT></P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 0.5in"><FONT =
face=3D"Courier New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">&#8226; Any =
of the following optional information: </SPAN></FONT></P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Courier =
New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">O Routers </SPAN></FONT></P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Courier =
New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">O Default route =
</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Courier =
New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">O DNS domain name =
</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Courier =
New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">O DNS servers =
</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Courier =
New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">O NIS domain name =
</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Courier =
New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">O NIS servers =
</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Courier =
New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">O WINS servers =
</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText style=3D"MARGIN-LEFT: 1in"><FONT face=3D"Courier =
New" size=3D1><SPAN style=3D"FONT-SIZE: 9pt">O SMTP server =
</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">3.) Lastly, there is still the possibility of =
using one of Zero Configuration (ZeroConf) technologies. There is no =
need to configure anything for this, hence the name &#8211; Zero =
Configuration). A browser plug-in is required though. Note that ZeroConf =
is Apple&#8217;s version of Microsoft&#8217;s UPnP. The link-local (LL) =
addressing feature uses addresses in the 169.254.0.0/16 range. Microsoft =
refers to this as &#8220;Automatic Private IP Addressing&#8221;. This =
technology is defined in RFC 3927 (for IPv4).</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">Bonjour is Apple&#8217;s implementation of =
ZeroConf. Avahi is the ZeroConf implementation for Linux and BSD. Avahi =
contains an implementation of IPv4LL in the avahi-autoipd tool (<A =
href=3D"http://avahi.org/download/avahi-autoipd.8.xml">http://avahi.org/d=
ownload/avahi-autoipd.8.xml</A>). This tool can be used stand-alone or =
as a plug-in for a DHCP client.</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">-Charissa</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">-----Original Message-----<BR>From: Jonathan =
Goldick <BR>Sent: Tuesday, May 01, 2007 1:37 PM<BR>To: Andy Sharp; =
dl-designreview<BR>Subject: RE: [Zonda] Network initial config via WebUI =
-- system component</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">In your backup method with a static IP, what =
number do we choose?&nbsp; We discussed this years back and could never =
come up with one that was known to be safe.&nbsp; We even went as far as =
talking about having a small input device to key in the static IP =
address (not a popular idea).&nbsp; </SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">In general I like the new idea, we should vet =
some of the assumptions with customers, like our newly formed customer =
advisory board, to see if this is what they want.&nbsp; Just thinking of =
possible issues relating to plugging a laptop directly into the 10x100 =
BaseT.&nbsp; Do we supply the cables?&nbsp; Must they have one of their =
own?</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">-----Original Message-----</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">From: Andy Sharp </SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">Sent: Tuesday, April 24, 2007 3:48 =
PM</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">To: dl-designreview</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">Subject: [Zonda] Network initial config via =
WebUI -- system component</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">I've heard that we are going to try and have a =
WebUI initial (install)</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">config thing for Zonda release, so I thought I =
would write up how I</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">think we should make the system level network =
part of that equation</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">happen.&nbsp; This what I planned to do for =
Linux regardless of how the</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">config was done, rather than use a serial =
port.</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">I'm asking for RFC at this time.&nbsp; If there =
are no objections or</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">questions, I'll schedule a meeting if people =
think it's necessary.</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">Cheers,</SPAN></FONT></P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoPlainText><FONT face=3D"Courier New" size=3D1><SPAN =
style=3D"FONT-SIZE: 9pt">a</SPAN></FONT></P></DIV></DIV></BODY></HTML>
------_=_NextPart_001_01C78E9D.A5FE1107--
